Subject: Postscript Blues

From: "jim (j.) cobban" <[email-masked]>
Date: Wed, 31 Aug 1994 09:26:00 -0400

Just to save others from wasting time the way I just have, there are some
problems with the Postscript version of the DLSw specification, at least
when you try to print it on a platform other than its native Windows.

 1) Windows always inserts superfluous <CR>s at the end of every line. 
    These are to satisfy the DOS text file standard, but they must be
    removed to satisfy some UNIX based Postscript drivers.  

 2) Windows always inserts an <EOT> in front of the %!PS-Adobe line.
    Since "smart" multi-language printers specifically look for a line
    starting with %! to invoke their Postscript driver this unnecessary
    extra character throws them off.  I have no idea why Windows feels this
    character is necessary. 

 3) The DLSw Postscript version has a whole extra line inserted at the front 
    of the file.  I suspect that this is intended to nudge some brain-dead PC
    printer into realizing that the file is Postscript.  This line starts
    with an <ESC> and continues with:

          %-12345X@PJL ENTER LANGUAGE = PostScript

Even with those changes, which are usually enough to get most documents to
print, I have not yet been able to get a print-out.  The UNIX Postscript
driver complains:

  Offending Command = setduplexmode
  Error = nametype : undefined
	      this name is not defined in a dictionary
  Stack = 
	      false

I am trying to print the Postscript version, because the text version, with
its excessively long lines, doesn't print in a readable format for me either.
I find this a handicap in trying to review the document.  If others are
having problems like this as well, that might explain the shortage of
comments on the document so far.

---

From: [email-masked] (Brad Cervenak)
Date: Wed, 31 Aug 1994 09:57:36 -0400 (EDT)

> when you try to print it on a platform other than its native Windows.

[ material deleted ]

> 	      this name is not defined in a dictionary

Jim,

I had the same problem when trying to view the file with Ghostscript.
I am no Postscript wizard, but I inserted the following line into the
dlsw012.psbin file:

/setduplexmode { pop } def

I inserted this line right after 'Win35Dict begin', which is around
line 154.

This worked fine for me.  You might want to try it...

Regards,

Bradford Cervenak
Proteon, Inc.
[email-masked]

---

From: [email-masked] (Brad Cervenak)
Date: Wed, 31 Aug 1994 09:55:05 -0400 (EDT)

[ material deleted ]

Jim,

Regards,

Bradford Cervenak ([email-masked])
Proteon, Inc.
Nine Technology Drive
Westborough, MA 01581